forked from elastic/logstash
-
Notifications
You must be signed in to change notification settings - Fork 0
pullu #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
pullu #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fix break_on_match issue while evaluating multiple patterns Closes elastic#1547 Make better exception message Add more specs for inputs with arrays Closes elastic#1547
Fix break_on_match issue while evaluating multiple patterns Closes elastic#1547 Make better exception message Add more specs for inputs with arrays Closes elastic#1547
use bundler compatible ruby version string
ES version 1.0 or greater is now supported by all protocols. The Elasticsearch eng team has tests to ensure client nodes from all ES versions >=1.0 work with all ES clusters version >=1.0
Update the example because output doesn't have the message parameter, instead it should use a a codec. Also update the way how logstash is executed.
Tilde '~' is a valid character in UNIXPATHs. Closes elastic#1195
Tests included. Note about grammar compilation: I had to use treetop 1.4.15 (1.5.3 generates ruby code that fails to parse, haven't spent any time debugging) Fixes elastic#1513
To avoid issues like: /etc/cron.daily/logrotate: gzip: stdin: file size changed while zipping This change is harmless and will prevent errors like this one
Update Gemfile for package testing
Remove the log parameter as web doesn't allow it
Add sprintf ability to room_id field in hipchat output
- Use better installer method to avoid documentation installation With the previous method it would install the documentation which didn't exist. - Create Fake gemspec info for logstash to help dependency management for plugins Previously we would create a real gem and install it to aid in dependency management for plugins and logstash Now we create a fake gemspec on the fly with the real version of logstash avoiding having to build it every time.
Previously the loading of the logstash gemspec was limited to the plugin manager After more tests we need the gemspec to be loaded for any action with the plugins Moving it to the environment module makes it available for more generic loading Make sure plugin manager uses new function for loading gemspec
Addresses elastic#1747. This removes the argument list iteration and spawning of multiple tasks. It's still possible to specify aditional arguments but now they're ignored. PR: elastic#1752
…own json parser Fixes elastic#1450
The filter should only modify the event's fields and tags if and only if all resolves/reverses succeed. So we clone the event, modify the new copy and return it if all operations succeed. Otherwise the original event is not modified. For performance reasons we could reverse the clone logic: clone the event, modify the original event and, it case of failure, return the backup. Note: this changes the dns filter behaviour towards add_tag Fixes elastic#1795
Improves upon elastic#1790 Fixes elastic#1803
- Move helper functions in own modules and extend Rspec - Refactor files into correct naming and paths - Modify files to use new spec_helper and helpers - Pin rspec to 2.14.x Fixes elastic#1758
- date speed test only run when performance is enabled Fixes elastic#1758
When doing randomized testing, one of the tests failed because kafka was not initialized yet Fixes elastic#1758
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.